Method and apparatus for a home network auto-tree builder

ABSTRACT

A method and system is provided for detecting, commanding and controlling diverse home devices currently connected to a home network. An interface is provided for accessing the home devices that are currently connected to a home network. According to the method, a device link file is generated, wherein the device link file identifies home devices that are currently connected to the home network. A device link page is created, wherein the device link page contains a device button that is associated with each home device that is identified in the device link file. A hyper-text link is associated with each device button, wherein the hyper-text link provides a link to an HTML page that is contained on the home device that is associated with the device button, and the device link page is displayed on a browser based home device.

CROSS-REFERENCES TO RELATED APPLICATIONS

This patent application claims priority from provisional patentapplication Ser. No. 60/050,762, filed on Jun. 25, 1997, entitled HomeNetwork, Browser Based, Command and Control and provisional patentapplication Ser. No. 60/059,499, filed on Sep. 22, 1997, entitledImproved Home Network, Browser Based, Command and Control, which areincorporated herein by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to the field of networks, and moreparticularly to providing an interface to access devices currentlyconnected to a home network.

2. Description of Related Art

A typical household contains several home devices. As used in thisdocument, the term “home device” encompasses all electronic devices thatare typically found in the home, with the exception of general purposecomputers (i.e. personal computers (PCs), laptop computers, etc). Forexample, the term home device includes but is not limited to suchelectronic devices as security systems, theatre equipment (e.g., TVs,VCRs, stereo equipment, and direct broadcast satellite services or(DBSS), also known as digital satellite services (DSS)), sprinklersystems, lighting systems, micro waves, dish washers, ovens/stoves, andwashers/dryers. Indeed, an automobile may be a home device. On the otherhand, the term “device” as used in this document may comprise logicaldevices or other units having functionality and an ability to exchangedata, and may include not only all home devices but also general purposecomputers.

In general, home devices are used to perform tasks that enhance ahomeowner's life style and standard of living. For example, a dishwasherperforms the task of washing dirty dishes and relieves the homeowner ofhaving to wash the dishes by hand. A VCR can record a TV program toallow a homeowner to watch a particular program at a later time.Security systems protect the homeowner's valuables and can reduce thehomeowner's fear of unwanted entry. Home devices (such as home theatreequipment) are often controlled using a single common control unit,namely a remote control device. This single common control unit allows ahomeowner to control and command several different home devices using asingle interface. Thus, many manufacturers have developed control unitsfor controlling and commanding their home devices from a singleinterface.

One drawback associated with using the remote control unit to commandand control home devices is that it provides static control and commandlogic for controlling and commanding each home device. Therefore, aparticular remote control unit can only control and command those homedevices for which it includes the necessary control and command logic.For example, if a remote control unit comprises logic for controlling atelevision (TV), a video cassette recorder (VCR), and a digital videodevice (DVD), but not a compact disk (CD) unit, the remote control unitcan not be used to command and control the CD unit. In addition, as newhome devices are developed, the remote control unit will not be able tocontrol and command the new home devices that require control andcommand logic that was not known at the time the remote control unit wasdeveloped.

Where a device, such as a remote control, is available for communicatingwith or controlling a plurality of home devices that are connected to ahome network, it is necessary to be able to identify the devices whichare currently connected to, and active on, the network.

Therefore, there is a need for a method of detecting, identifying andcreating links to the devices currently connected to the network. Also,there is a need for a mechanism that provides for dynamically updatingthe devices detected as connected to the network, and for rendering auser interface to enable user control and command of any device that iscurrently connected to the network.

SUMMARY OF THE INVENTION

It is accordingly an object of the invention to overcome the problems ofthe prior art, and to provide an interface for accessing home devicesthat are currently connected to a home network.

It is another object of the invention to provide a method and apparatusfor controlling any of a plurality of devices currently connected to thenetwork.

The present invention accordingly provides a method for providing aninterface for accessing home devices that are currently connected to ahome network, to enable a user to communicate with, to command and tocontrol such home devices.

In accordance with a feature of the invention, an interface foraccessing home devices is provided by a method which includes the stepsof generating a device link file, wherein the device link fileidentifies home devices that are currently connected to the homenetwork; creating a device link page, wherein the device link pagecontains a device button that is associated with each home device thatis identified in the device link file; associating a hypertext link witheach device button, wherein the hyper-text link provides a link to anHTML page that is contained on the home device that is associated withthe device button; and displaying the device link page on a browserbased home device.

According to one aspect of the invention, the device link file may begenerated by detecting that a home device is connected to the homenetwork; associating a logical device name with the home device; andstoring the logical device name in the device link file.

In accordance with another aspect of the invention, the device link pagemay be created by retrieving a logical device name from the device linkfile; storing the logical device name in the device link page; andconverting the logical device name to a device button.

In accordance with still another aspect of the invention, the hyper-textlink may be associated with each device button by retrieving a URL froma home device, wherein the URL is maintained in a properties fileassociated with the home device; and associating the URL with the devicebutton that is associated with the home device.

In accordance with yet another aspect of the invention, the manufacturerdevice button is stored in the device link page by storing themanufacturer device button in a user definable area of the device linkpage.

These and other objects, features and advantages will become morereadily apparent from the following description of a preferredembodiment of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

The objects and features of the present invention, which are believed tobe novel, are set forth with particularity in the appended claims. Thepresent invention, both as to its organization and manner of operation,together with further objects and advantages, may best be understood byreference to the following description, taken in connection with theaccompanying drawings, in which:

FIG. 1 is a block diagram of a home network constructed in accordancewith the present invention;

FIG. 2 illustrates an example of a layered interface model that can beused for communicating between home devices in accordance with thepresent invention;

FIGS. 3A and 3B are block diagrams illustrating controlling andcommanding of a home device using a browser based Digital TV (DTV)according to one embodiment of the present invention and a specificexample;

FIG. 4A is a block diagram illustrating a home device discoverymechanism according to one embodiment of the invention;

FIG. 4B depicts a flow diagram illustrating the generation of a devicelist file according to certain embodiments of the invention;

FIG. 5A is a block diagram of a device link page in accordance with thepresent invention;

FIG. 5B illustrates an example of a home device tree structure accordingto certain embodiments of the invention;

FIG. 6 graphically depicts a view of a device link page in accordancewith the present invention;

FIG. 7 graphically depicts an alternative view diagram of a device linkpage in accordance with the present invention;

FIG. 8 graphically depicts a preliminary view of a session page inaccordance with the present invention;

FIG. 9 is a block diagram illustrating a session manager causing twohome devices to communicate over a home network according to certainembodiments of the invention;

FIG. 10 graphically depicts a secondary view of the session page inaccordance with the present invention;

FIG. 11 graphically depicts a third view of the session page inaccordance with the present invention;

FIG. 12A is a block diagram of a session page in accordance with thepresent invention;

FIG. 12B is another block diagram of the session page in accordance withthe present invention;

FIG. 13 is another block diagram of the session page in accordance withthe present invention;

FIG. 14 is a block diagram of a home network that is connected to theInternet in accordance with the present inventions;

FIG. 15 is a diagram illustrating the creation of a macro according toone embodiment of the invention; and

FIG. 16 is a diagram illustrating the creation of a macro according toanother embodiment of the invention.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

The following description is provided to enable any person skilled inthe art to make and use the invention and sets forth the best modespresently contemplated by the inventors of carrying out their inventionof a method and apparatus for controlling home devices over a homenetwork. In the following description, for purposes of explanation,numerous specific details are set forth in order to provide a thoroughunderstanding of the present invention. It will be apparent, however, toone skilled in the art that the present invention may be practicedwithout these specific details. In other instances, well-knownstructures and devices are shown in block diagram form in order to avoidunnecessarily obscuring the present inventions.

In an exemplary embodiment of the present invention, a browser basedhome network uses Internet technology to control and command homedevices that are connected to a home network. Each home device containsinterface data (e.g. HTML, XML, JAVA, JAVASCRIPT, GIF, JPEG, graphicsfiles, or any other format useful for the intended purpose) thatprovides an interface for the commanding and controlling of the homedevice over the home network. In certain embodiments, each home devicecontains one or more Hypertext Markup Language (HTML) pages that providefor the commanding and controlling of the home device. Using the browsertechnology, the home network employs Internet standards to render theHTML pages in order to provide users with a plurality of graphical userinterfaces (“GUIs”) for commanding and controlling each home devices. Inone embodiment, the home network is configured as an intranet.

FIG. 1 is a block diagram of a home network 100 constructed inaccordance with one embodiment of the present invention. As depicted inFIG. 1, a 1394 serial bus 114 electronically connects multiple homedevices on the home network 100. In this example, the 1394 serial bus114 provides the physical layer (medium) for sending and receiving databetween the various connected home devices. The 1394 serial bus 114supports both time-multiplexed audio/video (A/V) streams and standard IP(Internet Protocol) communications. In certain embodiments, the homenetwork uses an IP network layer as the communication layer for the homenetwork 100. However, other communication protocols could be used toprovide communication for the home network. For example, the inventionmay be implemented using FCP (Function Control Protocol) as defined byIEC 61883, or any other appropriate protocol. Thus, a network maygenerally include two or more devices interconnected by a physical layerfor exchange or transfer of data in accordance with a predefinedcommunication protocol.

FIG. 2 illustrates an example of a layered interface model that can beused for communicating between home devices in accordance with thepresent invention. In this example, a home device (server) 150communicates with a home device client 166 using network communicationlayers 152–164. By employing the Internet Protocol standard for thenetwork layer 160, the home devices can communicate with each otherwithout having to know specific details about the other communicationlayers (i.e. application 152, presentation 154, session 156, transport158, data link 162 and physical 164). Thus, by employing the InternetProtocol standard for the network layer 160, the home network may use acombination of different communication layers in communicating betweendifferent home devices. It should be recognized that a single physicalpackage may include several devices which are logically networked via anetwork layer for example as shown in FIG. 2, not necessarily via aphysical network. Such devices may include a VCR and a TV in a singlehousing, for example. Thus, for such an embodiment, where a logicaldevice accesses a GUI to enable a user to control a home device, thehome device and the logical device may be included in the same physicalpackage. In such an embodiment, it could be considered that the physicaldevice fetches a GUI from itself. However, in other embodiments the homenetwork interconnects separate physical devices, wherein for example, afirst device fetches a GUI from a second device, to permit userinteraction with the GUI to control the second device.

By way of definition, it is contemplated that a “client” is a deviceproviding control interface service to a human operator, including agraphical display hardware for down communication and a mouse or otherpoint-and-click device for up (or return) communication. A “server” iscontemplated as a module supplying a service, which may be any serviceother than a control interface provided by a client. Stated differently,the server/client relationship is a control relationship, wherein theserver provides a service but a client may use the data, as a DTVdisplays video data, but does not manipulate or alter the data. It isthus consistent with this definition to observe that, frequently, aserver may be a source of information and a client (a browser, forexample) may be a consumer of information.

Some specific functions which may be implemented by servers include:return of information (data); performance of a function (e.g.,mechanical function) and return of status; return of a data stream andstatus; reception of a data stream and return of status; or saving of astate for subsequent action. Examples of servers include MPEG source,sink and display servers.

While a server typically includes a custom, built-in, control program toimplement control of its own hardware, a client functions to interfacewith the server. It should be noted, however, that a “server” as usedherein does not imply that a web server and a protocol stack must beused.

In a presently preferred embodiment, a 1394 serial bus is used as thephysical layer 164 for the data communications on the home network 100.Because of its enhanced bandwidth capabilities, the 1394 serial bus canprovide a single medium for all data communications on the home network100 (i.e. audio/video streams and command/control). However, the homenetwork 100 is not restricted to using a 1394 serial bus, and, inalternative embodiments of the present invention, other bus types, suchas Ethernet, ATM, wireless, etc., may be used as the physical layer ifthey meet the particular throughput requirements of an individual homenetwork.

As depicted in FIG. 1, the home network 100 has several home devicesconnected to the 1394 serial bus 114. In this example, the home devicesinclude a DBSS 104 which receives transmission signals from a satellite122 for subsequent display. Associated with the DBSS is a networkinterface unit (“NIU”) which, among other things, provides an interfacebetween the DBSS satellite transmissions and the 1394 serial bus 114.

A digital video device (“DVD”) 108 is also connected to the exemplaryhome network 100. The DVD 108 can be used to display digitally encodedvideos on a home television.

Also connected to the exemplary home network 100 is a digital videocassette recorder (“DVCR”) 10, i.e., a digital VCR, and a digital TV102.

In this example, the DTV 102 provides the human interface for the homenetwork 100 by employing browser technology to allow users to controland command the home devices over the home network 100. Unlike mostother home devices that are typically connected to a home network, theDTV 102 can provide the human interface for the home network 100 as itcomprises a screen for displaying HTML pages. However other home deviceshaving a display capability may be used to provide the human interface.Thus, in certain embodiments of the inventions, a device such as apersonal computer (“PC”) is used to provide the human interface for arespective home network, as a PC typically embodies a screen displayunit.

Although the 1394 serial bus 114 is depicted as using the HTTP/IPinterface protocol, certain home devices may require other protocolsinterface types (e.g. TCP/IP, UDP/IP, FTP/IP, TELNET/IP, SNMP/IP,DNS/IP, SMTP/IP). Therefore the HTTP/IP protocol may not be able tosatisfy all home device connection requirements. Thus, in certainembodiments of the invention, a bridge proxy 116 is used to interfacetwo networks using dissimilar interface protocols on their respectivemediums which, when connected, comprise the home network 100. In certainembodiments, the two network mediums are of the same type. For example,as depicted in FIG. 1, the 1394 serial bus 114 using the HTTP/IPinterface protocol is connected by a bridge proxy 116 to the 1394 serialbus 118, which uses the IEC61883 interface protocol. By using bridgeproxy 116 to interface between the HTTP/IP and IEC61883 protocols,security system 120, which uses the IEC 61883 interface protocol is alsoaccessible on the home network 100.

In certain other embodiments, a home network may be comprised of twonetwork mediums of dissimilar types, e.g., a 1394 Serial bus andEthernet. Therefore, in certain embodiments of the invention, a bridgeproxy is used to interface two dissimilar medium types to form a singlehome network.

The Dynamic Host Configuration Protocol (DHCP) server 106 is used forthe discovery of home devices that are powered on and connected to thehome network 100. The home device discovery process is described ingreater detail below.

Home Network Overview

As depicted in FIG. 1, DTV 102, DVCR 110, DVD 108, DSS-NIU 104 andsecurity system 120 represent home devices that are currently connectedto the home network 100. A client-server relationship exists among theattached devices, with the DTV 102 typically behaving as the client andhome devices DVCR 110, DVD 108, DSS-NIU 104 and security system 120behaving as servers.

As previously mentioned, each home device is associated with one or moreHypertext Markup Language (HTML) files. The HTML files define thecontrol and command functions associated with a particular home device.Each HTML file may also contain embedded references to other HTML files.The browser based DTV 102 (acting as a client), receives and interpretsthe HTML files associated with the home devices (acting as servers) andgraphically displays the respective control and command information onits viewable display.

By conforming to the Hypertext Markup Language (HTML) and HypertextTransfer Protocol (HTTP) Internet standards, each home device sends itscustom GUI to the browser based DTV 102. The browser based DTV 102receives the HTML files from the home devices over the home network 100using the HTTP protocol. Each HTML file contains specific control andcommand information for a respective home device. The HTML files enablethe browser based DTV 102 to graphically display control and commandinformation to a user for a particular home device. Therefore, becauseeach home device supplies its own GUI through its own HTML files to thebrowser based DTV 102, the browser based DTV 102 can provide a commandand control interface for a home device without having to know anyspecific details about the particular device. This feature allows thehome network 100 to contain home devices from a multitude of differentmanufacturers.

In addition, home devices can be transparently added or removed from thehome network 100 without affecting the overall system as, in accordancewith the invention, each home device defines its own command and controlinterface through its respective HTML files.

HTML Two Way Mechanism

FIG. 3A depicts an exemplary embodiment in which a browser based DTV 202(client) renders the characteristics of a home device 204 (server) overa home network. The home device 204 is represented by one or more HTMLfiles stored in an accessible area within the home device 204. The oneor more HTML files are ASCII text files containing specific informationpertaining to the particular home device 204, along with data thatenables a browser to present the information graphically. In addition torendering the HTML file on the browser based DTV 202, by employing formstechnology, the browser based DTV 202 can return information back to thehome device 204, thus providing a two-way communication. Other commontechniques for providing the two-way communication may include the useof Java or Control Gate Interfaces (CGIs). Once the informationcontained in a device's HTML file is graphically displayed on the DTV202, the user can control the home device 204 from the DTV 202 byselecting icons that have associated hyperlinks to start the controlprograms displayed on the DTV's screen and/or entering data to the DTV202.

Home Device HTML Files

As previously stated, each home device connected to the home network hasone or more associated HTML files. The HTML files for a respective homedevice define the control and command functions for that particular homedevice. Each HTML file may also contain embedded references to otherrelated HTML files. A device connected to the home network that has aviewable display (e.g., screen) and employs the browser technology mayreceive and interpret the HTML files associated with the home devicesconnected to the home network, and graphically display the informationcontained therein using a GUI on its screen.

This is illustrated by FIG. 3A wherein is shown an interaction between aclient and a server's executables. However, it is a feature of theinvention to provide control by interaction between executables of twoservers or of a client and plural servers. Thus, in accordance with theinvention control is typically implemented by service control programs(executables which are trying to be operated remotely), communications,commands and (if necessary), human interface with a server controlprogram via a GUI.

As one example, FIG. 3B shows location of file and program componentslocally, permitting control actions to be implemented by runningprograms and scripts on the device itself. This aspect of the inventionthus permits implementation to be carried out in a local manner whichmay be proprietary to the device rather than being performed remotely,and which thus does not require a standardized 1394 command set.

For example, the user may wish to change display brightness. Toimplement such a change, the user may click on a “Brightness” button onthe User HTML GUI page. In response, another GUI may be brought up, with“Bright” and “Dim” buttons. In response to the user clicking one ofthese two buttons, the http server will cause a brightness controlprogram for the display to run, in order to control the desired hardwareaction. For action local to the DTV, the DTV thus may include a servercapability, to interpret the post actions from the browser.

In that regard, in order to be able to post actions to control theirlocal hardware, all home network DTV devices preferably have a servercapability. For such operation, a browser may pick up local html filesand render the files to a GUI, without invoking the http server. Inorder to invoke the local http server to respond, clicking on a buttonpreferably involves an http access to the local machine name or IPaddress. In turn, the http server invokes the local device controlprogram, such as “Brightness” in the above example.

Generally, control may be implemented by transfer of a graphical controlobject (GCO), which preferably resides in the server, from the serverfor rendering on the client, to make the GUI. As an advantageous resultof this approach, detailed controls back to the server originating theGCO may be proprietary, as the server device “understands” and is awareof its own GUI controls. Additionally, the look and feel of the GUIoriginates with the attached server (e.g., the program server, serverdevice or media) and not with the client. Independence of the commandlanguage makes the arrangement operable independently of any newfeatures added to devices, which may be included in the GCO sent fromthe server, as well as any other future modifications, i.e., the homenetwork configuration is made inherently “new-feature proof” and “futureproof”.

Moreover, because a specific device may be selected for control byselecting an icon, there is no need for hardware reconfiguration toimplement control of different (or updated) devices. Accordingly, asingle command set may be used in a remote control for controllingplural (different) devices, by communicating with the client devicerendering of the GUI.

For server to server control without a GUI and user involvement,automatic operation may be initiated or set-up by user control via aclient, but later action is implemented by control language interactionbetween servers without involving a client.

In order to implement the foregoing, a server operating in accordancewith the invention preferably has one or more control programs forexecuting a required service. The server, which stores its GCO, providesthe GCO to a client and a GUI rendered on the client interfaces with theserver control program(s) executable(s). Moreover, the server controlprogram is able to save the state which has been controlled by the GUI,such as setting up a timer record action for example. The server alsomay include a clock for implementing various timer operations. Theclient is thus not required to have any knowledge of the server devicebeing controlled, and it is not necessary to provide the client with theability to save a previously controlled state. Indeed, as elsewheredescribed herein, the client may not be running for part of the time inwhich the server is running. Thus, preferably the server does not relyon another device, such as the client, for its operation and may servemultiple clients simultaneously.

A client, which receives GCO transfers from one or more servers,includes a GUI renderer to form the GUI from a received GCO. It iswithin the scope of the invention for a limited number of GCO's, for alimited number of servers, to reside in the client. However, for theinventive configuration of a home network, the large number of differentserver types presently in existence and contemplated for the futuredemonstrates the advantage arising from the GCO's residing on theservers, thus freeing the client from a requirement for any built-inknowledge of the server(s) being controlled.

In operation, during initial selection of the device, the GCO is fetchedand rendered by the client, to form the GUI and enable actions andresponses to be communicated between the GUI and the control program(s)of the client(s).

For server-server control, a command language interface and library ofcommands may be provided in a server. For any individual server, it isnot necessary to provide the entire command language. Instead, a servershould only be able to support those commands which it needs to send andreceive to perform its functions. It is a simpler task to provide such aconfiguration than to build in the command language interface andlibrary to a client for controlling all present and future servers.

In addition to the one or more HTML files stored therein, each homedevice connected to a home network contains a Properties file. In oneembodiment, the Properties file for a respective home device comprisesthe device manufacturer's name, the device name, the device type, thedevice model, and the Uniform Resource Locator (“URL”) of the devicemanufacturer's HTML home page. The top-level page associated with eachhome device may be called the device/default.HTML file.

Each home device connected to the home network also contains a LOGOimage file. A LOGO image file for a respective home device is a filecontaining an image that represents the manufacturer of the device. Inone embodiment, the LOGO image file for a particular home devicecontains an image with the name and logo of the manufacturer of the homedevice.

In the following description, a software agent which assists the user ininteracting with the network and controlling the various home devicesconnected to the network, and thus acts as the primary interface betweenthe user and the home network, is called a session manager. For example,the software agent for the user (i.e., the session manager) may accessthe devices to get more information for the user, in order to assist theuser with making selections associated with the devices, or withmanaging the devices. Such assistance with control of a device mayinclude modifying the GUI display for that device, as by graying outsome buttons, thus inhibiting selection of various options (or devices)based on prior selections and capabilities of devices. Still further,the session manager, acting as the user's agent, may link two or moredevices selected by the user and may set up a communication paththerebetween, freeing the user from the tedium and detail ofimplementing such control functions.

In certain embodiments, in order for a session manager to properlylocate the LOGO image file of a respective home device, all home devicesconnected to the home network use a standard filename for the particularLOGO image file to be displayed. In one embodiment, each home devicenames its respective LOGO image file that is to be displayed LOGO.GIF.

In certain embodiments, a LOGO image file for a respective home deviceis of a standard size, e.g. 120×40 pixels. A standard size ensures thatthe device logos have a neat, uniform look when depicted in the GUIdisplayed to the user. In certain embodiments, the image of the LOGOimage file may also be animated.

In certain embodiments, multiple versions of the LOGO image file mayreside on a respective home device, with the home device responsible fordetermining which version is ultimately displayed to the user. The homedevice may update the version to be displayed to the user over time,based on criteria of the device manufacturer's choosing.

Each home device connected to a home network also contains an ICON imagefile. An ICON image file for a respective home device is a filecontaining an image that represents the particular type of home device;e.g., a DTV or a DVCR. In certain embodiments, the ICON image filecontains an image of the device or a symbol that represents the type ofdevice. A manufacturer model number may be included at the bottom of theimage in the ICON image file, to assist in identification of the homedevice on the home network.

In certain embodiments, several variations of the ICON image file resideon a respective home device, with each ICON variation representing aparticular state of the home device. For example, for a DVCR, the ICONimage files may contain images of a DVCR playing, rewinding, mediainserted, media absent, etc.

To represent the various device state images, the manufacturer may use avariety of symbols, colors and animation. The home device is responsiblefor determining which ICON image version is to be displayed to the user,based on the device's representative state at any particular time. Thisallows the ICON image file for a respective home device to providefeedback to the user as to the particular state of the home device.

In certain embodiments, an ICON image file for a respective home deviceis of a standard size, e.g., 120×90 pixels. A standard size ensures thatthe device images will have a neat, uniform look when depicted in theGUI displayed to the user. In one embodiment, in order for a sessionmanager to properly locate the ICON image file of a respective homedevice to be displayed, all home devices connected to the home networkuse a standard ICON image filename for the respective ICON image file tobe displayed. Each home device may name its respective ICON image fileto be displayed ICON.GIF.

As previously stated, each home device connected to the home network hasone or more HTML files associated with it. One of these HTML files is ahome, or base page, file for the particular home device. To aid in theaccess of a particular home device's home page, in certain embodiments,each home device uses a standard home page filename. In one embodiment,each home device names its respective home page file USER.HTML.

Home Device Discovery Process

Communication on the home network is provided through the use of theTransmission Control Protocol/Internet Protocol (TCP/IP) standardnetwork protocols. The TCP layer provides a reliable delivery mechanismwhile the IP layer provides a routable addressing mechanism for packetsof data on the home network 100. In the home device discovery process,each home device is associated with a unique IP address and a logicalname, which are used to identify a particular home device connected tothe home network. To associate each home device with a unique IP addressand logical name pair, a configuration manager is provided thatdynamically allocates a unique IP address and logical name for each homedevice that becomes available on the home network. An available homedevice is a home device that is both powered-on and connected to thehome network.

The IP address and logical name pairs of the available home devices arestored in a device list file within the configuration manager. Thedevice list file is dynamically updated as home devices are added andremoved from the home network 100 (i.e., become available andnon-available on the home network 100).

By using the configuration manager to allocate unique IP addresses foreach home device, device manufacturers are relieved from having toassociate a predefined IP address with each home device. However, incertain embodiments of the invention, when a particular home device isassociated with a predefined IP address, the configuration manager usesthe predefined IP address as the home device's unique IP address on thehome network 100.

In one embodiment of the invention, a dynamic host configurationprotocol (“DHCP”) server 106 of FIG. 1 performs the functions of aconfiguration manager for a home network 100. The DHCP is a currentindustry standard and, for a particular home network, multiple homedevices may be capable of performing the necessary DHCP server 106functions. However, although multiple home devices may be capable offunctioning as the DHCP server 106, in a presently preferred embodiment,the home device that is of the device type least likely to be duplicatedon the home network 100 (i.e., least likely to have more than one of itshome device types resident on the home network 100) is nominated tofunction as the DHCP server 106. In the exemplary home network 100 ofFIG. 1, the DSS 104 is nominated to be the DHCP server 106 for the homenetwork 100 as it is least likely to be duplicated on the network 100.

The DHCP server 106 on the home network 100 generates a unique IPaddress and, for each home device that is available on the home network100, retrieves a logical name pair from the device. In certainembodiments, if an individual home device on the home network 100 has apredefined IP address already associated with it, the DHCP server 106uses the predefined IP address as the unique IP address from that homedevice. The DHCP server 106 causes the IP address and logical name pairsassociated with the available home devices to be stored within a devicelist file. The device list file is dynamically updated as home devicesare added and removed from the home network 100.

In certain configurations, a plurality of home devices with DHCP servercapabilities may exist on a single home network. Therefore, in certainembodiments, an arbitration protocol is employed to select and designatea particular home device to function as the DHCP server for the homenetwork. In another embodiment, a communication protocol is employedbetween the various home devices with DHCP server capabilities that arepresent on a home network, resulting in a single designated DHCP serverfor the home network.

FIG. 4A is a block diagram illustrating a home device discovery processaccording to an embodiment of the invention. When a home device 302 thatis connected to the home network is powered on, the home device 302broadcasts its presence over the home network in order to extract itsconfiguration from the DHCP server 306. Upon receiving the broadcast,the DHCP server 306 generates a unique IP address and a logical name tobe associated with the home device 302. After generating the unique IPaddress and looking up the logical name pair, the DHCP server 306returns the IP address and logical name pair to the home device 302. Theunique IP address is then used for communicating with the home device302 over the home network. In addition to sending the IP address andlogical name pair to the home device 302, the DHCP server 306 stores thegenerated IP address and logical name pair within the device list file.This discovery process is repeated for each home device that is poweredon and connected to the home network. Thus, the DHCP server 306 providesfor the dynamic allocation of IP address and logical name pairs forconfiguring newly attached and powered on home devices.

FIG. 3A depicts a flow diagram illustrating the generation of a devicelist file 318 according to certain embodiments of the invention. In thisexample, a DHCP Server 310 communicates with a home device 312 that isaccessible on the home network in order to generate a unique IP addressand logical name for the home device 312. The DHCP Server 310 storesthis information in the DHCP database 314. As home devices becomeavailable/non-available on the home network, the information in the DHCPdatabase 314 is continually updated in the manner described below.

GENIP is a Win32 console-based application which interacts with externalprograms, databases (indirectly) and device/session managers. The coreinteraction is an indirect contact with the standard DHCP Server productwhich is part of the standard Windows NT Server package, through aprogram known as DHCPCMD.exe, which is part of the NT Server Resourcekit found on MSDN developer DCROM sets. In operation, DHCPCMD.exeinteracts with the external programs and databases via a command“enumclients”, which creates a listing of all the current database ofDHCP clients. Thus, GENIP runs the DHCPCMD utility and generates aninternal “current” database of IP leases active in the DHCP databasefrom the output of the DHCPCMD utility.

The GENIP process 316 of FIG. 4B periodically reads the deviceinformation contained in the DHCP database 314 and compares it with thedevice information currently contained in the device list file 318. Bycomparing the information the GENIP 316 can determine if a home devicehas been added or removed from the home network. More specifically, the“current” database is compared item-for-item against the previously readdatabase and, if any differences are found, a database update isperformed thereby providing detection of any newly connected devices onthe home network.

In one embodiment, if the device information contained in the DHCPdatabase 314 differs from the device information contained in the devicelist file 318, the GENIP process 316 signals a process to update adevice link page and repaint a client display. The device link page isdescribed in greater detail below.

ReadDHCPDB( ) is the workhorse of GENIP, handling the setup andexecution of DHCPCMD as well 95 reading the resultant output therefrom,reading the same into the “current” database, comparing with the“previous” database, and then writing a new “output” database for theclients.

By default, GENIP operates on the DHCP database every 3 seconds, and itis thus advantageous to have GENIP running on the same physical machineas the DHCP server itself. Similarly, as the device and/or sessionmanagers will be accessing the output database frequently as well, theoutput file should be placed in a directory which is shared-out by theserver and to which the clients have access. Although this requiresagreement by the clients on where the output database is stored, thisfeature of the protocol may be improved upon by providing a protocolwhich both is non-polling for the events and also does not requiremanual configuration.

For example, instead of writing to a file, the UpdateDB( ) member ofGENIP may prepare a network packet which could be broadcast into thesubnet of interest, the packet containing instructions for the client onhow and where to get the latest database information. This may be simplyimplemented by using the http protocol, placed on an unused port such as8080 for example, so that the broadcast message would containhttp://server_ip_address:8080/network_db.txt. The “network_db.txt”portion of the message would not be used if the only use for port 8080is the network database. For improved future capability and expansionpurposes, other information would be allowed to be transmitted via thissame http port, and an actual full URL is provided.

Auto-TREE Builder

In one embodiment of the invention, an auto-tree builder uses thecontents of the device list file of a home network in order to generatea device link page. The device link page is displayed to the user on thescreen of a browser based home device. The device link page contains ahome device button for each home device identified in the device listfile. Each home device button in the device link page is associated witha hypertext link (hyperlink) to the top-level page of the respectivehome device. If a user selects a particular home device button containedin the device link page, the respective device's home page issubsequently displayed to the user on the browser based home device'sscreen.

FIG. 5B illustrates an example of a home device tree structure 400according to certain embodiments of the invention. In this example, thehome device tree structure 400 contains a device list file 410, a devicelink page 412 and three top-level device pages (DSS 414, DTV 416 and DVD418). Using the device information contained in device list file 410,the auto-tree builder generates the device link page 412 and insertslinks (e.g. hypertext links) to the top-level page of each device (DSS414, DTV 416 and DVD 418). In this example, the device page DSS containsseveral data files 420 that can be accessed via the link between thedevice link page 412 and the DSS top-level device page 414.

In certain embodiments, in generating the device link page, theauto-tree builder uses the device list file to create a device HTML filethat contains a home device button for each home device that iscurrently connected to the home network. Using the IP addressescontained in the device list file, the auto-tree builder accesses eachhome device to obtain the Properties file information and the URL of thetop-level page (i.e. USER.HTML file) associated with each home device.Using the respective URL information, the auto-tree builder convertseach home device button in the device HTML file to a hyper-text link tothe top-level page of the respective home device. This device HTML fileis then used as the device link page.

For example, FIG. 5A is a device link page 402 according to oneembodiment of the invention. As depicted, device link page 402 containshome device buttons 406 for each home device connected to the homenetwork 100. Each home device button 406 is associated with a hypertextlink to the top-level home page of the corresponding home device. If auser selects a particular home device button 406 contained in the devicelink page 402, the respective device's home page is subsequentlydisplayed to the user.

In certain embodiments of the invention, the auto-tree builder alsoretrieves the ICON.GIF image file that is stored in each home device.The auto-tree builder then uses the ICON.GIF images for displaying eachof the corresponding home device buttons.

In addition to the ICON images, in certain embodiments, the auto-treebuilder also obtains the LOGO.GIF image file for each home device. Theauto-tree builder associates each LOGO.GIF image with a hypertext linkto the home page of the device's manufacturer. The LOGO image is thenincluded in the device HTML file. For example, FIG. 6 is a device linkpage 502 according to one embodiment of the invention. As depicted, thedevice link page 502 contains home device buttons 504 and manufacturerdevice buttons 506. The home device buttons 504 are represented by theICON.GIF images of each corresponding device. The manufacturer devicebuttons 506 are represented by the LOGO.GIF images of the respectivemanufacturer of the corresponding home device.

In certain embodiments, as depicted in FIG. 7, the user may define thearrangement of device images 602 and logos 604 on the device link page606, according to his or her own criteria. For example, a user mayarrange the device images 602 and associated logos 604 in groupsaccording to the respective home device's placement in the home, e.g.,on a room by room basis. In such an example, a camcorder manufactured bySONY, a DTV manufactured by Samsung and a DBSS manufactured by Zenithmay all be grouped in a living room group 608. In this embodiment, theuser may also include additional text lines 610 to describe thegroupings and/or the devices depicted by the device images 602 andassociated logos 604.

Session Manager

As previously noted, a session manager provides the primary interfacebetween a user and a home network. The session manager, when properlyactivated, generates a session page that provides an interface whichallows users to command and control the home devices that are connectedto the home network in order to perform various functions and/orservices. Some typical services that are available on a home networkinclude, but are not limited to, starting a movie playing, programming aDBSS, and recording a television program.

The session manager displays available home network services (servers)and matches capabilities and selections made in one graphic userinterface (GUI) with another GUI to facilitate sensible and easyselection, thus simplifying use of the home network.

FIG. 9 is a block diagram illustrating a session manager 750 causing twohome devices (DTV 752, DVCR 754) to communicate over a home networkaccording to certain embodiments of the invention. As depicted in thisexample, by sending command and control information to the home devices(DTV 752, DVCR 754), the session manager 750 causes the home devices(DTV 752, DVCR 754) to communicate with each other (i.e. audio/videostream). For example, to display a recorded TV show, the session manager750 sends command/control information to cause the DVCR 754 to broadcastinformation (e.g. the TV show) on a particular stream over the homenetwork. In addition, the session manager 750 sends command/controlinformation to cause the DTV 752 to display the information that isbeing broadcast on the particular stream over the home network.

Similarly, though not shown in the drawing Figure, the session managermay send command/control information to cause a tuner (for example theDBSS) to broadcast a TV show on a stream over the network and may sendfurther command/control information to either or both the DTV and DVCRto display and/or record the TV show.

In still another alternate embodiment, if a single physical housing, orpackage, were to include both a DTV and a tuner (i.e., two separatelogical devices), the command/control information sent to the housingwould cause the tuner therein to broadcast a TV program on a stream overthe home network to either (or both) the DTV in the same housing and/orto the separately housed DVCR.

More specifically, client/server control actions may be implemented toinitiate an A/V program source stream and a sink server stream. Oncedata is flowing, the session manager client may disengage from thisactivity and perform other functions. In controlling the illustrativeconfiguration, the session manager may cause the DVCR 754 to save afirst state, e.g., “timer record”, and the DTV to save a second state,e.g., “timer select a program”. A clock later triggers the saved statesinto action. In this example, no further control actions are required ofthe session manager. However, for more complex examples, the sessionmanager may remain in, or regain, control, or may initiate furthercontrol of other devices.

Although the basic model illustrated in FIG. 9 shows one client and twoservers, one server representing the control program controlling the DTVas providing a display service and the other representing the controlprogram controlling the DVCR to provide a recording service, the modelcan be extended to a plurality of N servers where N>2.

FIG. 8 illustrates a session page 702 according to one embodiment of theinvention. In this example, the session page 702 contains frames 704,706 and 708. As depicted, frame 704 contains a device link page 710 thatcontains device buttons 712 for each home device currently connected tothe home network.

When the session manager is activated, it causes the auto-tree builderprocess to generate a new device link page. In certain embodiments, thesession manager is notified as home devices are dynamically added andremoved from the home network. For example, referring back to FIG. 4B,when the GENIP process 316 determines that a home device has been eitheradded to or removed from the home network, the GENIP process 316notifies the session manager. The session manger then causes theauto-tree builder process to generate a new device link page.

In an alternative embodiment, the session manager periodically polls thedevice list file 318 to determine if it has been updated with new homedevice information. If the session manger determines that device listfile 318 has been updated, the session manager causes the auto-treebuilder process to generate a new device link page.

In certain embodiments of the invention, the auto-tree builder processfunctions are contained within the session manager. Thus, in oneembodiment of the invention, the session manager generates the devicelink page by performing the previously described auto-tree builderfunctions.

A critical function of the session manager is to enable a user toinitiate an available service on the home network. An available serviceis a particular function that can be performed by one or more homedevices that are currently powered-on and connected to the home network.For example, a service may consist of selecting a DTV for viewing aparticular TV show and tuning the DBSS to a particular station that iscarrying the respective TV show.

To enable a user to initiate an available service, when the user selectsa particular home device button 712 from the device link page 710, thesession manger causes the top-level home page of the selected homedevice to be displayed within a frame contained in session page 702. Forpurposes of explanation, it shall be assumed that a user selects thedevice button 712 corresponding to “Dad's TV”.

As shown in FIG. 10, when the user selects the device button 712 forDad's TV, the session manager displays the top-level home page 804 forthe respective home device in a frame 706 of the session page 802. FIG.10 is similar to FIG. 8 and, therefore, like components have beennumbered alike. As depicted in FIG. 10, in certain embodiments of theinvention, the LOGO image 806 that is associated with the selected homedevice is displayed within the frame 706.

After a device image 712 is selected, the session manager continues todisplay the contents of the device link page 710. However, in certainembodiments, the selected device button 712 is deactivated and is,therefore, non-responsive for further selection by the user. Forexample, when the device button 712 corresponding to Dad's TV isselected, it is deactivated and becomes non-responsive to furtherselection by the user.

When the user selects a home device button 712, the session managerobtains the particular capabilities of the selected home device. Theparticular capabilities of a home device includes a list of standardnamed functions that the respective home device is capable ofperforming, e.g., the capabilities of a DVCR generally include“accepting video” and “displaying video”.

In certain embodiments, the session manager obtains the particularcapabilities of a selected home device by accessing a standard namedfile on the respective home device.

After obtaining the particular capabilities of the selected home device,the session manager searches the capabilities of the other home devicesthat are represented in the device link page 710 (i.e., listed in thedevice list file), for matches to the particular capabilities of theselected home device. For each home device found to have a matchingcapability to the selected home device, the session manager continues toactivate the respective device button 712 (i.e., maintains it responsiveto selection by the user). For each home device that is found to have nomatching capabilities to the selected home device, the session managerdeactivates the respective device button 712 (i.e., sets itnon-responsive to selection by the user) in order that the user may notfurther select the respective device for the current session.

For example, where the user has selected a client device such as a TVdisplay, the session manager may specifically search for matchingdevices which are capable of acting as video servers, or sources, ratherthan for other displays. Under such circumstances, the session managermay deactivate buttons for other displays. Alternatively, in a “controlonly” mode of operation, where a server-client relationship is not beingestablished, the session manager does not seek a second device which mayact as a source for the selected device.

More particularly, in accordance with the invention it is possible tooperate with a number of software agents representing devices which arecapable of controlling lights, for example. In such an environment, theuser would select both a control device, which is not a source or serverof information, and one or more light devices to be controlled thereby.When the user first selects the control device, the session manager maythen identify various devices capable of being controlled by, orinteracting with, the selected device and continue to activate therespective device buttons thereof, while deactivating the buttons forother devices. Indeed, it should be appreciated that the session managermay select any number of devices for presentation to the user aspossible choices for operation, for which the selection buttons remainactivated. The devices may or may not co-operate with each other. Thatis, the devices whose buttons remain activated may operate incooperation with, or independently of, each other.

Where an information presentation device is selected, it may be possiblethat a plurality of servers may remain active for possible selection.For example, in accordance with some embodiments of the invention, whena device button for a DTV or DVCR is selected, the session manager mayactivate device buttons for several information sources, such as anaudio server and a video server. Indeed, it is also possible that deviceselection buttons may remain activated for selection of plural videoservers, and that upon selection of one video server the buttons forselection of other servers will be maintained activated, to account forsituations wherein it is desired to provide multiple images on a singledisplay. For example, it may be desirable to display an entertainmentvideo while simultaneously displaying, as a picture-in-a-picture, videofrom a security camera or from another server. Alternatively, videoinformation from one or more sources may be communicated to a pluralityof client displays.

It should thus be appreciated that, as appropriate information oncapabilities of device interaction is provided to the session manager,the session manager will indicate that various of the devices are, orare not, enabled for selection by the user based on the user's priorselections. By acting as an agent for the user, the session managerobtains information relating to device capability and, in responsethereto, deactivates selection buttons for particular devices whilemaintaining active the device selection buttons for other devices. Bydetermining whether and which devices have matching capabilities, and bygraying out (deactivating) buttons for non matching devices andactivating buttons for matching devices, the session manager thusassists the user with making selections associated with the devices, orwith managing the devices.

With such assistance, the user may then select a second home device tointeract with the previously selected home device in order to performthe desired service. Where the session manager has inhibited someselection possibilities and enabled others, the user's selection issimplified. Where the matching, selection, inhibiting or enabling hasnot been carried out by the session manager, the user performs theselection based on various criteria. For example, the user may simplywish to select or activate a specific device. Alternatively, the usermay wish to select all devices capable of performing a specificfunction.

In that regard, the session manager may generate a page which includesall contents of the network, and all functional capabilities,independent of specific device. Thus, the HTML page may identifyservices available to the user by content, such as by providing a listof video or audio programs, etc., which are available on the homenetwork regardless of the device on which such content is beingprovided. Such a display is user transparent in the sense that the useris permitted to select information sources based on content, rather thanequipment, device or channel through which the information is madeavailable.

On selecting the second home device, the session manager displays thehome page for the second home device in frame 708. The order in whichframes are chosen for displaying the home page of each selected deviceis not critical, and therefore, in certain embodiments of the invention,the home page of the first selected device is displayed in frame 708 andthe home page of the second selected device is displayed in frame 706.

FIG. 11 illustrates session page 902 after the selection of a secondhome device according to one embodiment of the invention. As shown inFIG. 11, when the user selects the device button 712 corresponding toJim's DVD in this example, the session manager displays the top-levelhome page 904 for the respective home device in a frame 708 of thesession page 902. FIG. 11 is similar to FIG. 9 and FIG. 10 and,therefore, like components have been numbered alike. As depicted in FIG.11, in certain embodiments of the invention, the LOGO image 906associated with the selected home device is displayed within the frame708.

Once two home device images have been selected, the session managerallows the respective home devices to communicate with each other to setup and perform the desired service as selected by the user through theoptions displayed on the respective home pages 804 and 904 of eachselected home device.

An example of an embodiment of a session manager session 1002 isdisplayed in FIGS. 12A, 12B and 13. In this example, as depicted in FIG.12A, the user may choose one of four device images displayed in a devicelink page 1022 contained in frame 1004 of a session page 1012. In thisexample, the user may select a DSS device button 1014, a CD devicebutton 1016, a DTV device button 1018 or a DVCR device button 1020. Forexplanation purposes, it shall be assumed that the user selected theDVCR device button 1020.

As depicted in FIG. 12B, when the DVCR device button 1020 is selected,the session manager displays the home page for the respective DVCR inframe 1006 of the session page 1012. The session manager continues todisplay the four device images in the device link page 1022 of thesession page 1012. After the user selects the DVCR device button 1020,the session manager determines the particular capabilities of theselected DVCR device and compares them with the particular capabilitiesof the other accessible devices on the home network, i.e., the DBSS, theCD and the DTV.

In this example, the session manager determines that there is a match incapabilities between the selected DVCR and both the DTV and the DBSS.The session manager also determines that there is not a match betweenthe capabilities of the selected DVCR and the capabilities of the CD.Thus, the session manager deactivates the device button 1016 for the CDin the device link page 1022. Additionally, because the DVCR devicebutton 1020 was selected by the user, the session manager nowdeactivates the DVCR device button 1020 on the device link page 1022.

Because the session manager found matching capabilities between theselected DVCR and the DBSS and the DTV devices connected to the homenetwork, the session manager continues to keep the device buttons 1014and 1018 active for these respective home devices in the device linkpage 1022. Therefore, in this particular example, the user may nowadditionally select either the DTV device button 1018 or the DSS devicebutton 1014 in order that the selected respective device may interactwith the previously selected DVCR to perform a particular service on thehome network. However, because the CD device button 1016 has beendeactivated, as there are no shared capabilities between the CD and thepreviously selected DVCR, the user may not select the CD device button1016 at this time.

In this example, the user additionally selects the DTV button 1018contained in the device link page 1022.

As depicted in FIG. 13, the session manager then displays the home pagefor the respective DTV in frame 1008 of the session page 1012. Thesession manager continues to display the DVCR device's home page inframe 1006 and the four device buttons 1014, 1016, 1018 and 1020 in thedevice link page 1022 of the session page 1012. The user may now selectcontrol options from the home pages of each selected device (e.g., play1044 and volume 1042 respectively from the DVCR and the DTV home pages)in order to command and control the respective home devices to functionin a particular manner.

Any home device connected to a home network that can act as a client,i.e., which has the capability to display HTML files via is respectivedisplay unit (e.g., a DTV or a PC), may be designated a session server.A session server is a device that contains a session manager, a displayunit (i.e., screen), its own HTML page files, including a top-level,home HTML page file, and a browser.

In certain embodiments, when a session server (e.g., a DTV, generalpurpose computer) powers up, the associated session manager is executedand a session page, as discussed previously in FIG. 12A, is displayed onthe display unit of the particular session server. The user may thenselect a home device to command in order to perform a desired functionor service.

In an alternative embodiment, when a session server powers up, itsrespective browser runs and displays the top-level home page for therespective session server. In certain embodiments, the session server'shome page is associated with a standard filename, such as USER.HTML.Associated with the session server's home page is a device page buttonoption which, when selected, causes the session manager executing on thesession server to display a session page as discussed previously in FIG.12A.

Executing a Service

As previously indicated, the session manager is the primary interfacebetween the user and a home network. It is a tool capable of accessingand controlling every home device on the network, and, generally, shouldbe available on every browser-based home, i.e., client, device.

The session manager enables a user to begin a service on the homenetwork. As previously discussed, in relation to FIGS. 12A, 12B and 13,a session manager allows an user to choose up to two home devices at onetime, which he or she wishes to control to perform a specific service.

Each home device possesses one or more capabilities. For example, a DVCRis capable of both accepting and outputting a video signal, a CD playeris capable outputting an audio signal, and a DTV is capable acceptingvideo signal. Capabilities are either source-like or sink-like. A CDplayer posses a source-like capability as it is capable of outputting anaudio signal. In contrast, a DVCR possess both source-like and sink-likecapabilities as it can accept and output a video signal.

Each source-like capability has a complementing sink-like capabilitythat is compatible with it. For example, the outputting video capabilityof one home device is complemented by the accepting video capability ofa second home device. Each capability is associated with a certain setof data specifications. For example, when a DVCR outputs a video signal,the video signal is broadcast on a particular stream over the homenetwork. The stream number and other information about the signal formpart of the DVCR's (outputting home device) data specification message.Therefore, in one embodiment, to execute a session, a first home device(outputting home device) communicates a data specification message to asecond home device (accepting home device) via the session manager.

To provide for home device communication, each home device has a controlapplication associated with it. The control application for a homedevice handles the communication between the session manager of therespective home network and the home device. Therefore, the controlapplication for two respective home devices, provides a mechanism thatallows two home devices to communicate with each other via the controlmanager. In certain embodiments, the control application is adevice-specific packet of Java code that communicates with the hardwareof the respective home device, thereby controlling that home device.

By having a control application associated with each home device on thehome network, the control implementation details of the respective homedevice are grouped and maintained within a vendor-supplied deviceapplication. The control application of a home device further enablesthe respective vendors to provide their own control scenarios for theirdevices. All of the control applications of the home devices on the homenetwork, however, must comply with certain pre-defined specifications inorder to enable a respective home device to communicate with the sessionmanager.

In certain embodiments, each home device on the home network has a listof data specifications associated with it. For example, a DVCR that hasbeen instructed to “Output Video”, i.e., transmit a video signal,broadcasts the video signal on a particular isochronous stream. Thestream identification information and other details about the videosignal form part of the data specifications for the DVCR. The controlapplication of a home device, e.g., a DVCR, is capable of storing andadvertising the home device's data specifications when queried by thesession manager.

As previously discussed, the session manager can query various homedevices for their particular capabilities. The session manager is alsoresponsible for querying various home devices for their dataspecifications, in order to ensure the requested user service isproperly established and performed.

Once a user selects two home devices to perform a particular service,the user must choose certain device options for each of the selectedhome devices to perform that particular service. By choosing variousdevice options, the respective device's hardware is initialized toperform the service. The session manager coordinates the communicationbetween the selected devices to establish their hardware configurationsand to perform the requested service.

As an example, referring again to FIG. 13, if a user wishes to play avideo on the DTV, the service will consist of the playing of a video inthe DVCR and the displaying of the respective video on the DTV. Afterthe user selects the PLAY command option on the DVCR, the DVCR, amongother tasks, chooses the isochronous stream that the video signal willbe broadcast on. This information, as well as other pertinentinformation regarding the signal to be broadcast and the particular DVCRhardware setup for broadcasting, i.e., the data specifications of theDVCR for the PLAY service, are subsequently forwarded to the sessionmanager.

The session manager, upon receiving the data specifications from theDVCR, forwards the information to the DTV, in order that the DTV mayproperly initialize its hardware to display the video signal broadcastby the DVCR. Some time thereafter, the session manager deletes thesession page 1012 from the DTV display screen, allowing the DTV todisplay the video broadcast by the DVCR.

External Connection

Because the home network is Internet protocol compatible, connecting thehome network to the Internet can provide the advantage of being able tocontrol home devices from outside the home. Therefore, in certainembodiments of the invention, a connection is provided which allows thehome network to interface with the Internet. FIG. 14 depicts a homenetwork 1100 connected to the Internet 1102 in accordance with thepresent invention. Because many of the components in FIG. 14 are similarto FIG. 1, like components are numbered alike. As depicted in FIG. 14,in certain embodiments an Internet proxy 1104 is used to provide aninterface between the home network 1100 and the Internet 1102. Byproviding an interface between the home network 1100 and the Internet1102 a user can remotely control home devices connected to the homenetwork 1100. For example, if a user is required to work late and istherefore unable to watch the Monday night football game, the user canprogram a DVCR connected to their home network via the Internet, inorder to record the particular event.

Connecting the home network to the Internet can induce potentialsecurity access issues. Therefore, in certain embodiments, a securitymechanism is associated with the home network that is used to restrictaccess to the home network to particular authorized users.

Macros

As described above, a user must typically perform a sequence of steps inorder to cause a home device to execute a particular service. Inaddition, because users of a home network typically have dissimilarpreferences as to the particular settings of certain home devices, asequence of steps may be repeatedly performed in order to adjust thesettings of a respective home device. For example, a first user may havea particular preference as to the brightness, tint and/or contrast of aparticular DTV, while a second user has different preferences. To reducethe number of repeated steps typically performed by a user to set thesettings of a particular home device, in certain embodiments of theinvention a sequence of steps can be saved as a macro.

A macro is a sequence of commands that is saved in memory on a homedevice and which can be accessed and executed by a user. The macroexecutes as if the user actually selected a particular button orperformed a particular action from within a HTML page contained on therespective home device.

The use of macros can significantly reduce the amount of work that isrequired by a user to perform a particular function as a single macrocan be used to facilitate the convenient setup and control of severaldevices in tandem. For example, a user may want to record a particularTV program on channel 2 at 8:00 p.m. for 1 hour every Tuesday night.This normally requires the user to select a DBSS or DTV as the source ofthe program and to enter a particular sequence of steps to program aDVCR to receive and record the program. However, using a macro, the userneed only perform the step of executing the particular macro. The macrothen executes the necessary steps of selecting and commanding theparticular devices in order to record the program.

There are multiple ways of generating macros depending on the particularrespective home devices' software capabilities and the implementation oftheir HTML pages. In certain embodiments of the invention a preset typeof macro is used which saves the actual values of a device's parameters.The preset type of macro can be used in a home network in which theparameter values of a particular home device can be queried and set. Thepreset macro is created by saving the current value of a particular setof home device parameters. Each macro is associated with a name so thatit can be easily retrieved and executed at a later time. When a macro issubsequently executed it issues the appropriate commands to set thechosen parameters of the respective home device to their assigned value.

For example, FIG. 15 depicts the creation of a preset macro 1200according to one embodiment of the invention. As depicted in FIG. 15,when a create macro button 1202 on a respective HTML page of a homedevice is selected, a macro generation process 1204 begins to execute.Execution of the macro generation process 1204 causes a set of userselected device parameter values 1208, selected from the home device'sparameter list 1206, to be saved to a macro file 1210. The macro file1210 is assigned a unique macro name 1212 and saved on the home device.The macro name 1212 is saved as a macro name button on the home device'smacro list HTML page 1214. Thereafter, a user may select the macro namebutton, causing the respective macro file 1210 to be executed.

In one embodiment of the invention, a macro button is included on arespective home device's HTML home page. Selecting the macro buttoncauses the macro list HTML page 1214 to be displayed to the user. In oneembodiment, the create macro button 1202 is contained on the macro listHTML page 1214 for a respective home device.

In an alternative embodiment, a player piano macro is created by a homedevice's software and/or hardware saving the particular steps taken by auser while interacting with the device's HTML pages (e.g., the user'sbutton selections, data entries and/or cursor movements are saved asthey are executed by the user). Again, the created macros are associatedwith a particular name so that they may be easily retrieved and executedat a later time. When the player piano macro executes, it performs theparticular sequence of instructions as if the user was accessing therespective home device HTML page(s) and executing the sequence of stepsdirectly.

For example, FIG. 16 depicts the creation of a player piano macro 1300according to one embodiment of the invention. As depicted in FIG. 16,when a create macro button 1302 is selected a macro generation process1304 begins to execute. Execution of the macro generation process 1304causes a user interaction 1306 to be interpreted as a particular actionby a command interpreter 1308. The respective actions are copied into amacro file 1310, which is saved on the respective home device andassigned a unique macro name 1312. The macro name 1312 is saved as amacro name button on the home device's macro list HTML page 1314.Thereafter, a user may select the macro name button, causing therespective macro file 1310 to be executed.

In addition to the user created macros, in certain embodiments of theinvention, a predefined set of macros are stored in the respective homedevice's memory for access by a user. Because macros are typicallydevice dependent, in certain embodiments of the invention themanufacturer of a particular home device creates and defines a set ofmacros that can be executed on the respective home device.

Home Network Program Guide

To provide a user with a list of available multi-media material (e.g.,audio and video programs, TV programs, and CDs), one or more homenetwork program guides are associated with a home network. The one ormore home network programming guides may be categorized as to theavailable multi-media material on a particular home device or may becombined in various ways to depict a particular group of accessiblemulti-media material.

A television programming guide typically provides a list and schedule ofprograms that are available for viewing on a particular channel. Mostdigital satellite services provide programming information through anElectronic Programming Guide (EPG). The EPG displays a list of availableprograms and the specific time in which the programs can be viewedthrough the service. The EPGs are continually updated to reflect acurrent window of available programs. The home network uses the EPGinformation to build a home network HTML program guide. The HTML programguide is developed using the HTML standards and can be displayed on abrowser based home device. In addition, users can customize theparticular programming information that is displayed. For example, if auser would prefer not to display the schedule for a particular channel,e.g., because of its programming contents, the user may request thatchannel be removed from the HTML program guide.

The information contained in an EPG is dependent on the particular DBSSthat is used, and as such, there is currently no standard format fortransmitting this information. Therefore, in one embodiment of theinvention, a process extracts the information from a particular EPG andconverts it into a standard program format. The standard program formatis then used to build an HTML program guide. The HTML program guide canbe displayed on any browser based home device (e.g., a DTV or a PC).Like the EPGs, the HTML program guide is periodically updated to reflectthe currently available programs. As stated above, the user cancustomize the displayed HTML program guide to view only a particular setof the available information.

If an EPG format standard is developed, the HTML program guide can bebuilt without first converting the EPG information into the standardprogram format. Therefore, in certain embodiments of the invention, theHTML programming guide is built using a standard EPG format astransmitted by a particular DBSS.

In addition to the EPG received on a DBSS, the home network can beassociated with other home devices that contain multi-media material.For example, a DVD may contain certain movies, a PC may contain specificfiles (e.g., games, picture images), a DVCR may contain a particularmovie, and a CD player may contain specific CDs. In certain embodiments,each home device maintains an HTML program guide file that contains alist of the material currently available on the respective home device.Using a browser based home device, a user can display the availablematerial on a particular home device by rendering the particular homedevice's HTML program guide file.

In certain other embodiments of the invention, a multi-mediaidentification process is tasked with searching the accessible homedevices to determine what material is currently available on each ofthem. In one embodiment, the multi-media identification process accesseseach home device to obtain a file or directory that contains a list ofthe available material on the particular home device. A home devicecontents process then creates one or more HTML program guide files thatdepict the material currently available to the user. A user can displaythe available material by rendering a particular HTML program guidefile.

In an alternative embodiment, the multi-media identification processobtains the HTML program guide file that is maintained on a respectivehome device. Using the HTML program guide files obtained from theparticular home devices of the home network, the multi-mediaidentification process creates one or more HTML program guide files thatdepict the material currently available to the user. A user can displaythe available material by rendering a particular HTML program guidefile.

Conclusion

In accordance with the described invention, control of a plurality ofdevices (for example, a VCR, a CD player, a DVD player or any otherdevice) is implemented with the aid of a single control loop,established from a video display of a client device (such as a TV or aPC) to a user, to a remote control device, to a detector (such as an IRdetector) on the client device. Such a control loop is usable forcontrolling the plurality of devices, thereby eliminating a requirementfor front panel controls on such devices. In one form of the invention,the control loop may be implemented by connecting the devices to a homenetwork. Instead of using traditional front panel controls, theinvention thus provides for control of such devices through the homenetwork by interaction with the respective GUI thereof as rendered onthe client device. The invention also eliminates a requirement for aremote control device to include therein, or to have access to, controlcodes specific to each of the devices on the network. In theillustrative embodiment described herein, the remote control device mayfetch a GUI to provide the appropriate control function. In amodification, the remote control may include a display thereon fordisplaying the fetched GUI, thus eliminating a need for a separatedisplay on a client device. The invention thus permits the remotecontrol to access and control a plurality of devices using a singleremote control and a single display, with a single method of display andoperation, without requiring any change in the mode of operation thereofto change the device controlled thereby.

The foregoing description of the preferred embodiment of the inventionhas been presented for purposes of illustration and description. It isnot intended to be exhaustive or to limit the invention to the preciseforms disclosed, since many modifications or variations thereof arepossible in light of the above teaching. All such modifications andvariations are within the scope of the invention without departing fromthe broader spirit and scope of the invention. The embodiments describedherein were chosen and described in order best to explain the principlesof the invention and its practical application, thereby to enable othersskilled in the art to utilize the invention in various embodiments andwith various modifications as are suited to the particular usecontemplated therefor. It is intended that the scope of the invention bedefined by the claims appended hereto, when interpreted in accordancewith the full breadth to which they are legally and equitably entitled.The specification and drawings are, accordingly, to be regarded in anillustrative rather than a restrictive sense.

Those skilled in the art will appreciate that various adaptations andmodifications of the just-described preferred embodiments can beconfigured without departing from the scope and spirit of the invention.Therefore, it is to be understood that, within the scope of the appendedclaims, the invention may be practiced other than as specificallydescribed herein.

1. A method for providing an interface for accessing home devices thatare currently connected to a home network, the method comprising thesteps of: generating a device list file in an autonomous and dynamicmanner, wherein the device list file identifies home devices that arecurrently connected to the home network, and periodically refreshing thedevice list file by: autonomously detecting that a home device iscurrently connected to the home network, associating a logical devicename with the home device, and storing the logical device name in thedevice list file; creating a device link page, wherein the device linkpage contains at least one graphical or textual representation ofcorresponding devices that are identified in the device list file;associating a hyper-text link with each device representation, whereinthe hyper-text link provides a link to a web page that is contained inthe device that is associated with the device representation; anddisplaying the device link page on a browser based device.
 2. The methodof claim 1, wherein the step of creating the device link page includesthe step of: retrieving a logical device name from the device list file;storing the logical device name in the device link page; and convertingthe logical device name to a device button.
 3. The method of claim 1,wherein the step of creating the device link page includes the steps of:retrieving a device ICON image from a home device; creating a devicebutton based on the device ICON image; and storing the device button inthe device link page.
 4. The method of claim 1, wherein the step ofcreating the device link page includes the steps of: retrieving a deviceLOGO image from a home device; creating a manufacturer device buttonbased on the device LOGO image; and storing the manufacturer devicebutton in the device link page.
 5. The method of claim 4, wherein thestep of storing the manufacturer device button in the device link pageincludes the steps of storing the manufacturer device button in a userdefinable area of the device link page.
 6. The method of claim 1,wherein the step of associating a hyper-text with each devicerepresentation, includes the steps of: retrieving a URL from a homedevice, wherein the URL is maintained in a properties file associatedwith the home device; and associating the URL with the devicerepresentation that is associated with the home device.
 7. The method ofclaim 6, wherein the step of retrieving the URL from the home deviceincludes the steps of retrieving the URL from a properties file that isstored on the home device.
 8. The method of claim 1, wherein the stepsof generating the device list file further includes the steps ofdynamically and autonomously updating the device list file as devicesare connected to the home network.
 9. The method of claim 1, wherein thesteps of generating the device list file further includes the steps ofdynamically and autonomously updating the device list file as devicesare disconnected from the home network.
 10. The method of claim 1,wherein the steps of generating the device list file further includesthe steps of dynamically and autonomously updating the device list fileas devices are connected to, and disconnected from, the home network.11. The method of claim 1, wherein the steps of generating the devicelist file further includes the steps of autonomously determining thenetwork location and availability of the devices that are connected tothe home network.
 12. The method of claim 11, wherein the steps ofgenerating the device list file further includes the steps ofdynamically and autonomously updating the device list file as devicesare connected to the home network.
 13. The method of claim 11, whereinthe steps of generating the device list file further includes the stepsof dynamically and autonomously updating the device list file as devicesare disconnected from the home network.
 14. The method of claim 11,wherein the steps of generating the device list file further includesthe steps of dynamically and autonomously updating the device list fileas devices are connected to, and disconnected from, the home network.15. An agent that provides an interface for accessing home devices thatare currently connected to a home network, the agent comprising: a listfile generator that generates a device list file in an autonomous anddynamic manner, wherein the device list file is dynamically refreshedperiodically to identify home devices that are currently connected tothe home network; a link page generator that creates a device link page,wherein the device link page contains at least one graphical or textualrepresentation of corresponding devices that are identified in thedevice list file, the device link page further including a hyper-textlink associated with each device representation, wherein the hyper-textlink provides a link to a web page that is contained in the device thatis associated with the device representation; and a renderer thatdisplays the device link page on a browser based device as a graphicuser interface.
 16. The agent of claim 15 further comprising a sessionmanager that matches device capabilities and user selections in onegraphic user interface with device capabilities and user selections inanother graphic user interface, to facilitate compatible deviceselection, thus simplifying use of the home network.
 17. The agent ofclaim 16 wherein the session manager further enables a user to initiatean available service on the home network that can be performed by one ormore home devices by: obtaining particular capabilities of a selectedhome device by accessing the selected device; searching particularcapabilities of other home devices listed in the device link page formatches to the particular capabilities of the selected home device; foreach other home device found to have a matching capability to theselected home device, allowing the user to select that other homedevice.